Skip Headers

Oracle® Transparent Gateway for Informix Administrator's Guide 10g Release 2 (10.2) for Solaris Operating System (SPARC) Part Number B14275-01 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# Preface

This manual describes the Oracle Transparent Gateway for Informix, which enables Oracle client applications to access Informix data through Structured Query Language (SQL). The gateway, with the Oracle database server, creates the appearance that all data resides on a local Oracle database server, even though the data can be widely distributed.

This preface covers the following topics:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

## Audience

This manual is intended for Oracle database administrators who perform the following tasks:

- Installing and configuring the Oracle Transparent Gateway for Informix

- Diagnosing gateway errors

- Using the gateway to access Informix data

  Note: You should understand the fundamentals of transparent gateways and the Solaris Operating System (SPARC) before using this guide to install or administer the gateway.

## Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at

`http://www.oracle.com/accessibility/`

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

## Related Documents

For more information, see these Oracle resources:

- Oracle Database New Features

- Oracle Call Interface Programmer's Guide

- Oracle Enterprise Manager Administrator's Guide

- Oracle Database Administrator's Guide

- Oracle Application Developer's Guide - Fundamentals

- Oracle Database Concepts

- Oracle Database Performance Tuning Guide and Reference

- Oracle Database Performance Planning

- Oracle Database Error Messages

- Oracle Database Globalization Support Guide

- Oracle Database Reference

- Oracle SQL Reference

- Oracle Net Services Administrator's Guide

- SQL*Plus User's Guide and Reference

- Oracle Database Heterogeneous Connectivity Administrator's Guide

- Oracle 2 Day DBA

- Oracle Database Security Guide

Many of the examples in this book use the sample schemas of the seed database, which is installed by default when you install Oracle. Refer to Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself.

## Conventions

This section describes the conventions used in the text and code examples of this documentation set. It describes:

- Conventions in Text

- Conventions in Code Examples

Conventions in Text

We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.

Convention | Meaning | Example
--- | --- | ---
Bold | Bold typeface indicates terms that are defined in the text or terms that appear in a glossary, or both. | When you specify this clause, you create an index-organized table.
Italics | Italic typeface indicates book titles or emphasis. | Oracle Database Concepts Ensure that the recovery catalog and target database do not reside on the same disk.
`UPPERCASE monospace (fixed-width) font` | Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles. | You can specify this clause only for a `NUMBER` column. You can back up the database by using the `BACKUP` command. Query the `TABLE_NAME` column in the `USER_TABLES` data dictionary view. Use the `DBMS_STATS`.`GENERATE_STATS` procedure.
`lowercase monospace (fixed-width) font` | Lowercase monospace typeface indicates executables, filenames, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, usernames and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. | Enter `sqlplus` to open SQL*Plus. The password is specified in the `orapwd` file. Back up the datafiles and control files in the `/disk1/oracle/dbs` directory. The `department_id`, `department_name`, and `location_id` columns are in the `hr.departments` table. Set the `QUERY_REWRITE_ENABLED` initialization parameter to `true.` Connect as `oe` user. The `JRepUtil` class implements these methods.
`lowercase italic monospace (fixed-width) font` | Lowercase italic monospace font represents placeholders or variables. | You can specify the `parallel_clause`. Run `U` `old_release``.SQL` where `old_release` refers to the release you installed prior to upgrading.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:

    SELECT username FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use.

Convention | Meaning | Example
--- | --- | ---
    [ ]
| Brackets enclose one or more optional items. Do not enter the brackets. |
    DECIMAL (digits [ , precision ])
    { }
| Braces enclose two or more items, one of which is required. Do not enter the braces. |
    {ENABLE | DISABLE}
    |
| A vertical bar represents a choice of two or more options within brackets or braces. Enter one of the options. Do not enter the vertical bar. |
    {ENABLE | DISABLE}
    [COMPRESS | NOCOMPRESS]
    ...
| Horizontal ellipsis points indicate either: That we have omitted parts of the code that are not directly related to the example That you can repeat a portion of the code |
    CREATE TABLE ... AS subquery;

    SELECT col1, col2, ... , coln FROM employees;
    .
     .
     .
| Vertical ellipsis points indicate that we have omitted several lines of code not directly related to the example. |
    SQL> SELECT NAME FROM V$DATAFILE;
    NAME
    ------------------------------------
    /fsl/dbs/tbs_01.dbf
    /fs1/dbs/tbs_02.dbf
    .
    .
    .
    /fsl/dbs/tbs_09.dbf
    9 rows selected.
Other notation | You must enter symbols other than brackets, braces, vertical bars, and ellipsis points as shown. |
    acctbal NUMBER(11,2);
    acct    CONSTANT NUMBER(4) := 3;
    Italics
| Italicized text indicates placeholders or variables for which you must supply particular values. |
    CONNECT SYSTEM/system_password
    DB_NAME = database_name
    UPPERCASE
| Uppercase typeface indicates elements supplied by the system. We show these terms in uppercase in order to distinguish them from terms you define. Unless terms appear in brackets, enter them in the order and with the spelling shown. However, because these terms are not case sensitive, you can enter them in lowercase. |
    SELECT last_name, employee_id FROM employees;
    SELECT * FROM USER_TABLES;
    DROP TABLE hr.employees;
    lowercase
| Lowercase typeface indicates programmatic elements that you supply. For example, lowercase indicates names of tables, columns, or files. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. |
    SELECT last_name, employee_id FROM employees;
    sqlplus hr/hr
    CREATE USER mjones IDENTIFIED BY ty3MU9;